5.3.3 APPX Application Design Manual

+ Chapter 1-1: Overview of Application Design
+ Chapter 1-2: Getting Started
+ Chapter 1-3: Data Dictionary
+ Chapter 1-4: Understanding Process Design
+ Chapter 1-5: Interprocess Communication
+ Chapter 1-6: Customizing Your Application
+ Chapter 1-7: The Documentation Facility
+ Chapter 1-8: Application Design Tools
+ Chapter 2-1: Data Dictionary Overview
+ Chapter 2-2: Data Dictionary Concepts
+ Chapter 2-3: Domains
+ Chapter 2-4: Files and Fields
+ Chapter 2-5: Work Fields
+ Chapter 3-1: Overview of APPX Processes
+ Chapter 3-2: Getting Started
+ Chapter 3-3: Process Definition
+ Chapter 3-4: Menu Processes
+ Chapter 3-5: Job Processes
+ Chapter 3-6: Input Processes
+ Chapter 3-7: Output Processes
+ Chapter 3-8: Update Processes
+ Chapter 3-9: Query Processes
+ Chapter 3-10: Inquiry Processes
+ Chapter 3-11: Status Processes
+ Chapter 3-12: Subroutine Processes
+ Chapter 3-13: Table Processes
+ Chapter 3-14: Automatic and Optional Children
+ Chapter 3-15: Using the Image Editor
+ Chapter 3-16: Using GUI Features of the Image Editor
+ Chapter 3-17: Using Event Points
+ Chapter 4-1: ILF Integration
+ Chapter 4-2: True/False Status Indicators
+ Chapter 4-3: Specifying Statements
+ Chapter 4-4: The ILF Editor
+ Chapter 4-5: The Appx ILF Debugger
- Chapter 4-6: ILF Keyword Reference
+ Chapter 4-7: Predefined Fields
+ Chapter 4-8: Runtime Subroutine's and Predefined Processes
+ Chapter 4-9: Appx Chart Director API

Chapter 4-6: ILF Keyword Reference

TRAP


The TRAP statement temporarily halts execution at runtime to permit debugging. Debugging permits 'browsing' through the statements in an ILF routine, setting and clearing TRAP statements in those event points, stepping through the statements or event points,and inspecting and/or modifying variables.

  ?????   TRAP 
  (1)

(1) T/F execution conditions

Using the Statement

A TRAP statement can be used in any ILF routine in any event point in any process. The true/false indicators can be used to make a TRAP conditional. See The Debugger for details on using the debugger.

Restrictions

TRAP is executed only when the application is invoked from 'Test Application' within the application design utilities, or when invoked from the Toolbox there.

Statement Ignored

TRAP is ignored if the application is invoked from 'Select Database.'

Example

In the following example, the TRAP statement allows the designer to explore and observe the execution of this routine, which assigns a batch control number to a group of adjustments. 

        LABEL    :CHECK TRXCNTRL
        TRAP
        IF       TAR PARAM TRXCNTRL                EQ      1
  T     SET      TAR TRXCNTRL CONTROL NO           =  TAR PARAM ADJUST CONTROL
  T     COMPUTE  TAR PARAM ADJUST CONTROL          +      1
  T     SET      TAR TRXCNTRL APPLICATION          =  TAR
  T     SET      TAR TRXCNTRL FILE POSTED          =      ADJUSTMENTS
  T     SET      TAR TRXCNTRL OPERATOR ID          =  --- USER ID
  T     READ     TAR TRXCNTRL       HOLD 1 FT 1 BY TRXCNTRL KEY
  TT    GOTO     :CHECK TRXCNTRL

Application Design Manual                                         "Powered by Appx Software"

707

©2006 By APPX Software, Inc. All Rights Reserved